(C) Copyright 1995-1996 Novell, Inc. All rights reserved worldwide.
Welcome to the release of NetWare Client for Mac OS 5.11. This NetWare Client Read Me file contains information about component enhancements, known anomalies and, when available, work-arounds for these problems. This read me file contains two sections: the first section covers NetWare Client for Mac OS workstation software, and the second section covers NetWare Client for Mac OS server software (NLMs).
If you have any questions or concerns please contact Novell Macintosh Client Support at (800) NETWARE within the U.S.; outside of the U.S. please call 801-861-5588.
CLIENT WORKSTATION SOFTWARE NOTES -
• NW Client Installer 5.11
No known problems. If you are using Open Transport, ensure that you are using at least version 1.1.
• MacIPX 1.3.1
PROBLEM #1: MacIPX may display an error message containing the error code -94 when trying to use the Ethernet 802.3 frame type with certain Ethernet adapters.
SOLUTION: Install AppleTalk version 58 or later on your workstation. To obtain AppleTalk version 58 or later, contact the manufacturer of your Ethernet adapter. You can also obtain AppleTalk from Apple's Network Software Installer, version 1.3 or later.
PROBLEM #2: Some third-party applications use their own IPX protocol stacks, and do not use MacIPX. MacIPX may not function properly in their environments, depending on how MacIPX is configured.
SOLUTION: Contact the application vendor and request a version of the application that works with MacIPX. If none is available, you can configure MacIPX to use a network interface setup that is different than the network interface setup used by the other IPX protocol stack. For example, if the application's IPX protocol stack is using the Ethernet 802.3 frame type, you can configure MacIPX to use a different frame type such as 802.2. If this solution is impractical in your situation, you can configure MacIPX to use the LocalTalk network interface rather than the interface in use by the other IPX stack (such as Ethernet). However, this solution requires you to install and configure a MacIPX gateway somewhere on your network. Instructions for MacIPX gateway installation and configuration are located in the NetWare operating system documentation.
PROBLEM #3: Applications using MacIPX cannot locate any services when MacIPX is configured to use the AppleTalk interface.
SOLUTION: Ensure that MacIPX is using a valid MacIPX Gateway and that the Gateway is running on a NetWare server that will reply to Get Nearest Server requests.
PROBLEM #4: MacIPX may not work with some versions of Apple’s Power Macintosh 9500.
SOLUTION: The Operating System and Open Transport software components found on the early releases of the Power Macintosh 9500 are incompatible with MacIPX. In the U.S., you can obtain later revisions of this software by ordering an "update" CD for the Power Macintosh 9500 through 1-800-SOS-APPLE. For customers outside of the U.S., please contact your local Apple sales office.
PROBLEM #5: Applications using MacIPX may experience a loss of connectivity when running on Power Macintosh 7200, 7500, 8500, and 9500s using Open Transport 1.0.x.
SOLUTION: Install Open Transport 1.1.
PROBLEM #6: MacIPX does not load properly on workstations that use the Mac Password utility.
SOLUTION: Remove Mac Password from your system.
• NetWare Client 3.0
PROBLEM #1: If the UPGRADE LOW PRIORITY THREADS server parameter is set to OFF, and an NLM is loaded which prevents Low Priority Threads from running, (as is the case with MACFILE.NLM, under heavy load conditions) then a client may be unable to connect to the server and will encounter an alert during authentication such as, "Unknown Error -251".
SOLUTION: Issue the following command on the server:
SET UPGRADE LOW PRIORITY THREADS = ON
You may also choose to include this command in the AUTOEXEC.NCF file on the server.
CHANGES FROM 5.1:
1) The packet burst protocol is now supported for file reads/writes. This should boost file I/O performance.
2) NetWare Client for Mac OS now supports multiple NDS trees. You will be able to authenticate to and to browse multiple DS trees simultaneously.
3) ‘NetWare Client’ is now a system extension and not a Control Panel. To configure, now choose the ‘Configure...’ option in the Novell Login Menu.
4) The configuration of the client has been reworked to support multiple trees and to allow you to browse to locate users and containers.
5) The ‘Manage Connections...’ option in the Novell Login Menu has changed to ‘Connections...’. This now allows you to logout of individual trees or servers or to dismount volumes. You can now get information about trees, servers, or volumes.
6) The ‘Logout’ option in the Novell Login Menu has changed to ‘Logout Completely’. This choice now logs you out of all Novell servers and trees. (Previously it logged you out of DS and broke all DS connections.)
7) When logging into a tree you can now browse to locate your user object if unauthenticated browsing is allowed.
• NetWare Directory Browser 1.1
PROBLEM #1: Several beta sites reported a crash while using Apple Guide with the NetWare Directory Browser. Apple Guide would crash when attempting to display a coach mark around something other than a menu title.
SOLUTION: The cause of this problem has been isolated to Apple Guide version 1.2.5 on PowerPC-based systems. If the Apple Guide version 1.2.5 extension is replaced with an older (1.2) or newer (1.2.7) version, the problem does not occur. Our assumption is that Apple Guide 1.2.5 must have some bad Mixed Mode Manager calls. Older versions weren't native (no Mixed Mode Manager calls at all), and newer versions must have caught and fixed the bug.
PROBLEM #2: If you install on a 7.1 system you will not be able to drag Directory Services Objects to the desktop from the NetWare Directory Browser.
SOLUTION: Upgrade to a later system release or use the "Save to a Folder" or "Save to the Desktop" commands from the File menu.
CHANGES FROM 5.1:
Multi-Tree Support: The Log Out From Tree and Change to Tree items in the File menu are gone because they were needed only because of the previous single-tree restriction. Similarly, you are no longer prompted to Login when the Browser is launched. If you login to a tree after you have started browsing it, you may choose the Refresh Window command from the Browse menu to browse the current container again with your current authorization.
• NetWare File Access 1.1
PROBLEM #1: File creation times are not preserved when the files are copied to NetWare File Access volumes and when operated on by certain applications. This causes problems for applications such as installers that require that file creation times be preserved.
SOLUTION: NetWare File Access can set a file or directory's creation time only if the user is supervisor equivalent. This is due to a problem in the NetWare server. To work around the problem, either log on as the server administrator or use AppleShare to mount volumes for which you require that creation dates be preserved (for example, if you are moving an installer and its files to a NetWare server). An update release will contain patches for the problem on existing servers and a new NetWare File Access that will take advantage of the fixes.
PROBLEM #2: When using QuarkExpress with the Autosave feature enabled, files cannot be saved to an NetWare File Access volume more than one time after they have been opened.
SOLUTION: Turn off Autosave feature and make saves manually.
PROBLEM #3: Some applications create temporary files in the root directory of the volumes on which they are being executed. If you do not have write access privileges to the root of that volume the application will not be able to create these files.
SOLUTION: You need to be given write access to the root of the volume or use AppleShare to mount volumes from which these applications will be run.
• NetWare Object Assistant 1.0
No known problems.
• NetWare Print Access 1.1
PROBLEM #1: Some PostScript downloading or LaserWriter utilities may not recognize or use NetWare Print Queues selected using the NetWare Print Chooser. Normally they should respond with a “Printer not found” message.
SOLUTION: Use a utility that communicates with the printer currently selected in the Chooser, such as Adobe SendPS. Such utilities generally work with NetWare Print Access on the printer or queue most recently selected in the NetWare Print Chooser.
PROBLEM #2: Error code -8993 occurs when printing in the background with NetWare Print Access using the LaserWriter/PSPrinter 8.x driver.
SOLUTION: This problem is rare, and thought to be a result of the driver timing out due to not getting enough processor time. If you experience this problem, switch to foreground printing, or try to avoid intensive activity on your workstation when background printing is in progress.
PROBLEM #3: When using the NetWare Print Chooser to select LaserWriter/PSPrinter 8.1.2 or higher, the following alert may appear when Setup is started: “Autosetup failed, reverting to manual setup.”
SOLUTION: This alert indicates that the driver is looking for information about the target printer's installable options. NetWare Print Access does not have this information. Click OK and manually indicate the printer's installed options, to the best of your knowledge.
PROBLEM #4: When using the LaserWriter driver versions 8.0, 8.2, or 8.2.2 to print, the Macintosh workstation sometimes hangs.
SOLUTION: Some versions of Apple’s LaserWriter 8 driver have a bug which causes a hang when it tries to download a variation of the Helvetica font. To verify that this is the problem, turn background printing off in NetWare Print Chooser and print. Watch to see if the Macintosh hangs while displaying the message "Creating Screen Font: Helvetica" or "Downloading Helvetica-Oblique".
To work-around this issue:
1) Choose another print driver. LaserWriter versions 7.x, 8.1.1, and 8.3 do not suffer from this problem.
OR
2) After selecting the driver in the NetWare Print Chooser, use the "Setup" button to select a PPD file for the printer. This allows NetWare Print Access to tell the driver that Helvetica is already present on the printer so that it isn't downloaded.
OR
3) After selecting the object in the NetWare Print Chooser, check the "Assume Standard Fonts" box under the "NetWare Options..." button. This allows Netware Print Access to tell the driver that Helvetica is already present on the printer so that it isn't downloaded.
PROBLEM #5: When printing in the background, the following message may appear:
There is not enough memory to print "<document>" from "<application>" on printer "<printer>". Do you want PrintMonitor to adjust its memory size and try again?
SOLUTION: Some versions of Apple’s PrintMonitor by default allocate too little memory to accommodate NetWare Print Access. To correct this problem, you can hit the "Adjust Memory Size" button in the above alert; you may be required to select this options two or more times successively before you can successfully print. Alternatively, you can select the "Cancel Printing" option and manually adjust PrintMonitor's memory size. Click on the PrintMonitor application in the System:Extensions folder and select "Get Info" from the file menu. In the "Memory Requirements" area, set "Preferred size:" to at least 120K. Then try printing again.
PROBLEM #6: When printing to a queue or printer object residing on a 4.1 or earlier 4.x server, two short (less than 60 characters) print job notification messages appear in rapid succession referring to one job. This may happen when print notification is turned on and you are printing to a queue (or referenced printer object) without being logged into the server where the queue physically resides.
SOLUTION:
1) Turn off notification
2) Log into the matching server
3) Use a queue or printer object on a 4.11 or later server
PROBLEM #7: Jobs from QuarkExpress, Adobe Photoshop, or other applications which have the option of sending the data in binary format will not print successfully with a postscript error or images may print with artifacts or noise .
SOLUTION:
1) Many Mac applications that output graphics have the option in the application's Page Setup or Print dialog window to send the data in either Binary or ASCII format. Choose ASCII format.
2) If your printer supports it, have the network administrator set up the Printer object to support binary communications over a non-binary communications channel. Netware Print Access will then encode the binary data properly.
PROBLEM #8: When printing with LaserWriter 8.3.x, to a queue residing on a 3.x (non DS) server, which is made available to a Directory Tree via NetSync or Bindery Reference Queue mechanism, will occasionally get an error: "The LaserWriter 8 Preferences file may be missing or damaged. Please go to your Chooser and reselect your printer (Error -8969)."
SOLUTION:
1) Use a LaserWriter version 8.2.x or earlier
2) Print to a queue residing on a Directory Services (4.x) Server.
PROBLEM #9: While Shiva Config control panel version 3.7.3 is installed on a 68k Mac, a crash may occur when using the Network Control panel to switch between different AppleTalk protocols, such as between LocalTalk and EtherTalk, or AppleTalk Remote Access and EtherTalk.
SOLUTION:
1) Use a Macintosh based on the Power PC processor. This problem does not happen using Power PC Macs.
or
2) Remove the Shiva Config control panel from the Control Panels folder.
3) Use an updated version of the Shiva Config control panel when available.
• NetWare Print Chooser 1.1
PROBLEM #1: If you run NetWare Print Chooser concurrently with Apple's Chooser, the two applications may compete for ownership of the print drivers and thereby lead to serious problems, including crashes.
SOLUTION: Run only one chooser at a time.
PROBLEM #2: In the case where a NetWare Directory Services print queue object has multiple AppleTalk network address attributes with different NBP types--for example, the spooler is advertised by more than one ATPS spooler--NetWare Print Chooser may not enable all of the appropriate AppleTalk print drivers in the driver list.
SOLUTION: Such Directory Services objects may be rare at your site, in which case you would seldom encounter this problem. If the situation does arise, you will simply be limited in your choice of print drivers.
PROBLEM #3: When you first add a print driver extension to your Extension folder, the icon for that driver may not show correctly in NetWare Print Chooser.
SOLUTION: NetWare Print Chooser gets its icons from the desktop database. Eventually the desktop will get updated and the correct icons will display. If you wish to accelerate this process, try opening the Extensions folder on your desktop, forcing Finder to acknowledge that icon. The next time you run NetWare Print Chooser, it will show the correct icon.
PROBLEM #4: If you log out of the tree while NetWare Print Chooser is still running and then proceed to switch drivers and/or setup driver options, you may experience problems or even crash.
SOLUTION: The best thing to do is to quit the application before logging out of the tree.
PROBLEM #5: With GX installed, NetWare Print Chooser does not allow you to select a print driver.
SOLUTION: This version of NetWare Print Chooser does not support GX. You must remove GX from your system if you wish to use NetWare print services.
CHANGES FROM 5.1:
1) Added Multi-Tree support.
• NetWare UAM 5.1
No known problems.
• NetWare Volume Mounter 1.1
PROBLEM #1: Workstations using System 7.1 may find that the NetWare Volume Mounter does not stagger the windows, but stacks new windows directly on top of old ones.
SOLUTION: There is no solution at this time. To work around this problem move the windows off of each other manually.
CHANGES FROM 5.1:
1) Added Multi-Tree support.
• Remote Console 1.0
No known problems.
• ~NetWare Aliases 1.1
PROBLEM #1: Aliases made to a file or folder on a network volume mounted with NetWare Volume Mounter will not resolve correctly in System 7.1.1 if the volume is already mounted via AppleShare. Aliases to a volume will resolve correctly in all cases.
SOLUTION: Upgrade to System 7.5.
• NetWare/IP Macintosh Client 2.1
PROBLEM #1: Preferred DSS and NWIP servers must be configured in the Control Panel Settings dialog using the same format. ie, all entries must be entered as either IP addresses or names.
SOLUTION: There is no solution at this time.
PROBLEM #2: NetWare/IP may exhibit poor performance when running over MacTCP in some circumstances.
SOLUTION: To enhance performance use Open Transport 1.1 or later if your Macintosh can use Open Transport.
SERVER SOFTWARE NOTES -
• PINSTALL.NLM and NWCMACC.NLM 1.0
PROBLEM #1: There are several ways to change the volume name displayed on the workstation when mounting a server volume. One way is through the set commands in MACFILE.NLM. (Type "MACFILE HELP” in the NetWare server’s system console when MACFILE.NLM is loaded for more information.) Another way is through AFPCON.NLM when using NetWare for Macintosh. Volume name changes will not take effect dynamically. The indiscriminate changing of Macintosh volume names with these utilities and with AFPCON can result in unexpected volume names. (Last saved wins.)
SOLUTION: There is no solution at this time. To work around this issue, remount the volume on the workstation to see the new volume name.
PROBLEM #2: NWCMACC.NLM can incorrectly identify message and client files that do not belong to the product. For example NWCMACC will locate the NetWare for Macintosh installation directory as a source.
SOLUTION: There is no solution at this time.
• MACFILE.NLM 1.01
PROBLEM #1: If a volume is dismounted from the server while MACFILE.NLM is rebuilding a desktop database, error messages indicating that MACFILE.NLM cannot find files on the volume will be displayed on the console.
SOLUTION: Wait to dismount a volume until rebuilding is complete.
PROBLEM #2: Only a few items at a time are removed at MACFILE.NLM load time from a trash can abandoned by a crashed Macintosh.
SOLUTION: Unload and reload MACFILE.NLM again with the empty option. For example: LOAD MACFILE EMPTY.
PROBLEM #3: Icons for files on a NetWare volume do not appear in the
Finder; generic icons are displayed.
SOLUTION: Rebuild the desktop on the client workstation. Before mounting any NetWare volumes with the Mac name space, make sure that MACFILE.NLM is loaded on the server to which the volumes are attached and that the desktop has been reset on the desired NetWare volumes.
PROBLEM #4: An application on a NetWare volume is not added to the desktop during rebuild/reset; icons for that application are also not added.
SOLUTION: This may be caused by either of two things:
1) The 'bundle bit' for the application may not be set.
The solution is to set the bundle bit, using ResEdit or another Macintosh resource editor.
2) The resource fork of the application is corrupt.
File corruption may be due to a variety of reasons; it may be benign or possibly hazardous.
Minor file corruption may be disregarded but serious file corruption may indicate the presence of a virus. Severe file corruption may even cause the server to crash during rebuild and should be removed from the server. If a file is corrupt but, for some reason, you wish to leave it on the server, you may be able to prevent problems during rebuilds by clearing the 'bundle bit'.
MACFILE issues warnings when corrupt files are encountered. You may obtain more detailed information about file corruption by doing the following:
1) Issue the following command at the console: SET MACFILE FILELOG=3
2) Issue the following command at the console: MACFILE RESET DESKTOP ON
<Volume Name>
3) Examine the error messages during RESET, by opening the file
